home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19980424-19980901
/
000150_news@newsmaster….columbia.edu _Fri May 29 12:28:22 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id MAA24425
for <kermit.misc@watsun.cc.columbia.edu>; Fri, 29 May 1998 12:28:21 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id MAA02950
for kermit.misc@watsun; Fri, 29 May 1998 12:28:20 -0400 (EDT)
Path: news.columbia.edu!sol.ctr.columbia.edu!gondor!newshub.sdsu.edu!news.sgi.com!news-peer-west.sprintlink.net!news.sprintlink.net!newsfeed.wli.net!ais.net!news.msfc.nasa.gov!info.usuhs.mil!news.monroe.army.mil!wrdiss1.robins.af.mil!wpdiss1.wpafb.af.mil!oodiss1.hill.af.mil!news.cc.utah.edu!news.cs.utah.edu!cc.usu.edu!ivie
From: ivie@cc.usu.edu (Roger Ivie)
Newsgroups: comp.protocols.kermit.misc,comp.sys.hp48
Subject: Re: Kermit on the HP48 (Was: One-Way Transfer)
Message-ID: <3FmrftJsqL4F@cc.usu.edu>
Date: 26 May 98 09:39:21 MDT
References: <35646665.EBB3868B@theriver.com> <wk67iy1b8j.fsf@jhuapl.edu> <6kc4vm$ssl$1@apakabar.cc.columbia.edu>
Organization: Utah State University
Lines: 18
Xref: news.columbia.edu comp.protocols.kermit.misc:8814 comp.sys.hp48:81598
In article <6kc4vm$ssl$1@apakabar.cc.columbia.edu>, fdc@watsun.cc.columbia.edu (Frank da Cruz) writes:
> No good deed goes unpunished. The conservative original design of the
> protocol (to protect users from nontransparent connections) resulted in
> so much heckling from the ZMODEM contingent that we now allow the user to
> specify a list of control characters that may be unprefixed. This is,
> strictly speaking, in violation of the protocol definition, and as such
> it is not (and, as explained previously, can not be) negotiated at the
> protocol level.
>
> Nevertheless, the sample code that accompanies the protocol definition
> (op.cit., p.231) allows for bare control characters to be received.
What's the point in having a spec if the code, not the spec, is correct?
--
-------------------------+----------------------------------------------------
Roger Ivie | "You got advice for me. Well I'm telling you,
ivie@cc.usu.edu | I know nothing and I like it that way"
http://cc.usu.edu/~ivie/ | -- Eggplant